Skip to content

[schema-coverage] feat: Add schema coverage demo for max-turn-cache-misses field#40753

Merged
pelikhan merged 1 commit into
mainfrom
schema-demo-max-turn-cache-misses-54b7470eb55de2d9
Jun 22, 2026
Merged

[schema-coverage] feat: Add schema coverage demo for max-turn-cache-misses field#40753
pelikhan merged 1 commit into
mainfrom
schema-demo-max-turn-cache-misses-54b7470eb55de2d9

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds a single new demo file that exercises the max-turn-cache-misses frontmatter field, closing the last gap in schema feature coverage for the schema-demos/ collection.

What changed and why

File Change Notes
schema-demos/schema-demo-max-turn-cache-misses.md Added New workflow demo illustrating the max-turn-cache-misses frontmatter field; brings schema demo coverage to 100%.

Impact assessment

Dimension Value
Breaking change No
Impact level Low
Files changed 1 (new file only)
Runtime behaviour affected No

Field reference

max-turn-cache-misses — Maximum number of consecutive AWF cache misses allowed before the API proxy blocks further requests. The demo sets this to 5.

Testing / Verification

  • No production code was modified; this is a documentation/demo artefact.
  • Verify that schema-demos/schema-demo-max-turn-cache-misses.md is valid against the project workflow schema.
  • Confirm no duplicate max-turn-cache-misses demo already exists.

Generated by PR Description Updater for issue #40753 · 37 AIC · ⌖ 6.7 AIC · ⊞ 4.5K ·

@github-actions

Copy link
Copy Markdown
Contributor Author

Hey @github-actions 👋 — thanks for the automated schema coverage demo for the max-turn-cache-misses field! The new file fits neatly into the established schema-demos/ pattern and the PR body clearly explains the field semantics and the coverage motivation.

One thing worth noting:

  • No test files in the diff — the Schema Feature Coverage Checker workflow generates the demo .md file, but there is no corresponding automated validation that the demo workflow itself can be parsed/linted without errors. If the coverage checker already validates the generated file before opening the PR, this is fine; if not, a quick schema-lint step would harden this flow.

If you would like to address that gap, here is a ready-to-use prompt:

Add a lightweight validation step to the Schema Feature Coverage Checker workflow that runs the gh-aw schema linter (or equivalent frontmatter parser) against every newly generated schema-demo-*.md file before opening a pull request. This ensures the generated files are syntactically valid and the max-turn-cache-misses (and future fields) are correctly formatted before the PR is created.

Generated by ✅ Contribution Check · 153 AIC · ⌖ 15.6 AIC · ⊞ 5.9K ·

@github-actions github-actions Bot mentioned this pull request Jun 22, 2026
@pelikhan pelikhan marked this pull request as ready for review June 22, 2026 14:43
Copilot AI review requested due to automatic review settings June 22, 2026 14:43
@pelikhan pelikhan merged commit 42a1743 into main Jun 22, 2026
4 checks passed
@pelikhan pelikhan deleted the schema-demo-max-turn-cache-misses-54b7470eb55de2d9 branch June 22, 2026 14:43
@github-actions

github-actions Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor Author

🧠 Matt Pocock Skills Reviewer has completed the skills-based review. ✅

@github-actions

github-actions Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor Author

PR Code Quality Reviewer completed the code quality review.

@github-actions

github-actions Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor Author

Design Decision Gate 🏗️ completed the design decision gate check.

No ADR enforcement needed: PR #40753 does not have the 'implementation' label and has 0 new lines of code in business logic directories (default threshold is 100). Both enforcement conditions are false.

@github-actions

github-actions Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor Author

Test Quality Sentinel completed test quality analysis.

No test files were added or modified in this PR. The only change is schema-demos/schema-demo-max-turn-cache-misses.md (a markdown file). Test Quality Sentinel skipped.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a minimal schema demo workflow to exercise the max-turn-cache-misses frontmatter field, improving schema feature coverage for gh-aw workflows.

Changes:

  • Added a new schema demo markdown workflow showcasing max-turn-cache-misses: 5.
  • Included a minimal noop task body to keep the demo execution side-effect free.
Show a summary per file
File Description
schema-demos/schema-demo-max-turn-cache-misses.md New schema demo workflow demonstrating the max-turn-cache-misses frontmatter key with a noop task.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 1/1 changed files
  • Comments generated: 0

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No blocking issues — APPROVE

Single new file schema-demos/schema-demo-max-turn-cache-misses.md follows the established schema-demo pattern exactly.

Frontmatter (engine: codex, timeout-minutes: 5, permissions: contents: read, max-turn-cache-misses: 5) is consistent with peer files. Task body noop format matches all other schema demo files. No logic errors, security issues, or correctness concerns in the changed lines.

🔎 Code quality review by PR Code Quality Reviewer · 36.5 AIC · ⌖ 7.34 AIC · ⊞ 5.1K

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Skills-Based Review 🧠

Applied /grill-with-docs — approving with a minor documentation suggestion.

📋 Key Themes & Highlights

Key Themes

  • Missing field metadata in description: The What ... Does section describes the field purpose but omits the internal config mapping, env var override, and default value — context that peer demos include and that makes the file useful beyond just coverage.

Positive Highlights

  • ✅ Consistent structure with all existing schema demos (schema-demo-max-runs.md, schema-demo-max-tool-denials.md, etc.)
  • ✅ Correct engine choice (codex) for an AWF-proxy-level field
  • ✅ Valid frontmatter, appropriate timeout-minutes, and permissions: contents: read
  • ✅ Clean, minimal implementation that achieves its schema coverage goal

🧠 Reviewed using Matt Pocock's skills by Matt Pocock Skills Reviewer · 52.5 AIC · ⌖ 7.45 AIC · ⊞ 6.5K

## What `max-turn-cache-misses` Does

Maximum number of consecutive AWF cache misses allowed before the API proxy
blocks further requests.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[/grill-with-docs] The What ... Does description omits the internal field mapping and default value that make similar demos more useful as reference documentation.

💡 Suggestion

Other demos include the internal mapping in their description. For example, schema-demo-max-runs.md reads:

Deprecated legacy alias for AWF invocation cap (apiProxy.maxRuns). Use max-turns instead.

The PR body template attempted to include this metadata (Maps to <field>. Precedence: frontmatter value → <env_var> env override → built-in default <default>.) but the placeholders were left empty, and that information did not make it into the committed file body either.

Consider enriching the description — something like:

Maximum number of consecutive AWF cache misses allowed before the API proxy
blocks further requests. Maps to `apiProxy.maxTurnCacheMisses`. Precedence:
frontmatter value → `AWF_MAX_TURN_CACHE_MISSES` env override → built-in default `10`.

(Adjust the field path, env var, and default to match the actual schema values.)

This makes the demo genuinely educational rather than just a coverage stub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants